Distributed autonomic solutions repository

ABSTRACT

Managing software is provided. A solution to a problem that has occurred with a program on a client data processing system is received by a server. This solution is created while solving the problem that occurred on the data processing system. The solution includes a process that may be executed on another data processing system to solve the same problem on that data processing system. The process is, for example, a script, a macro, or a set of computer executable steps or instructions. A database of solutions is selectively updated to reflect the new solution. In response to a request for a solution by another client system to a problem, the server will respond with the current solution that exists in the database.

This application is a continuation of application Ser. No. 10/687,176, filed Oct. 16, 2003, now U.S. Pat. No. 7,318,226 issued Jan. 8, 2008.

CROSS REFERENCE TO RELATED APPLICATIONS

The present invention is related to an application entitled Method and Apparatus for a Self Healing Agent, Ser. No. 10/687,273, filed even date hereof, assigned to the same assignee, and incorporated herein by reference in entirety for all purposes.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates generally to an improved data processing system and in particular to a method and apparatus for managing software. Still more particularly, the present invention relates to a method, apparatus, and computer instructions for providing autonomic solutions for the repair and/or configuration of a stand-alone or network data processing system.

2. Description of Related Art

When a data processing system, such as a workstation or personal computer fails or breaks down, a system administrator or service engineer is tasked with finding the cause of the failure and providing a solution or fix to the failure. The system administrator or engineer uses their knowledge along with other materials and resources to diagnose the problem and repair the data processing system. The engineer may use various diagnostic software programs, as well as consult knowledge bases. The knowledge of what to change on the data processing system, how to make a change, and other information is usually found in a knowledge base. This knowledge base takes the form of bulletins, frequently asked questions (FAQs), tips, and techniques. However, the fix or solution to the problem is often the result of applying some or all of the recommended fixes in a manner that depends on the knowledge and experience of the administrator or engineer. This person combines the information and knowledge available to them and performs some set of steps to diagnose and provide a solution to the problem.

This knowledge is often never recorded or specified in a manner to allow others to use the information to diagnose and repair a similar problem, nor is the knowledge ever transferred to others who could benefit from the solution created by the administrator or engineer. In some cases, the engineer may post a solution or provide a frequently asked question (FAQ) entry on a Web site. Users of the Web site can attempt to locate a particular fix or solution by searching for the text of the symptoms. An example of this type of searchable database is the Microsoft Knowledge Base, which is available from Microsoft Corporation.

The knowledge may be obtained from this person by word of mouth if another administrator or engineer encounters a similar problem. Those who become experts in the field are continually called upon to perform a specific or specialized task with respect to solving problems with software. These problems may occur in many different situations. For example, problems may occur in a data processing system when adding a user, installing a program, or applying a patch. Further, problems also occur during the normal operation of the data processing system when a failure or error occurs.

In many cases, the user having a problem on a data processing system must wait for an expert or person with knowledge of the specific problem to come to their location and provide a solution to the problem. The system administrators and engineers often have numerous requests for aid and prioritize these requests based on their perceived severity of the problem. As a result, many users may become frustrated with waiting for a solution to a problem based on the demands and requests of the administrator or service engineer.

Therefore, it would be advantageous to have an improved method, apparatus, and computer instructions for managing such failures in a data processing system.

SUMMARY OF THE INVENTION

The present invention provides a method, apparatus, and computer instructions for managing software. A solution to a problem that has occurred with a program on a client data processing system is received by a server. This solution is created while solving the problem that occurred on the data processing system. The solution includes a process that may be executed on another data processing system to solve the same problem on that data processing system. The process is, for example, a script, a macro, or a set of computer executable steps or instructions. A database of solutions is selectively updated to reflect the new solution. In response to a request for a solution by another client system to a problem, the server will respond with the current solution that exists in the database.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

FIG. 1 is a pictorial representation of a network of data processing systems in which the present invention may be implemented;

FIG. 2 is a block diagram of a data processing system that may be implemented as a server in accordance with a preferred embodiment of the present invention;

FIG. 3 is a block diagram illustrating a data processing system in which the present invention may be implemented;

FIG. 4 is a diagram illustrating components used in a distributed autonomic solutions repository with accordance with a preferred embodiment of the present invention;

FIG. 5 is a diagram illustrating an illustrative example of a solution in accordance with a preferred embodiment of the present invention;

FIG. 6 is a diagram illustrating a distribution of a solution from an autonomic knowledge base in accordance with a preferred embodiment of the present invention;

FIG. 7 is a flowchart of a process for identifying a diagnosis for a problem in accordance with a preferred embodiment of the present invention;

FIG. 8 is a flowchart of a solution or repair process in accordance with a preferred embodiment of the present invention;

FIG. 9 is a flowchart of a process for handling a solution received from an agent in accordance with a preferred embodiment of the present invention;

FIG. 10 is a flowchart of a process for updating a local rules database in accordance with a preferred embodiment of the present invention; and

FIG. 11 is a flowchart of a process for sending updates in a knowledge base to an agent in accordance with a preferred embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference now to the figures, FIG. 1 depicts a pictorial representation of a network of data processing systems in which the present invention may be implemented. Network data processing system 100 is a network of computers in which the present invention may be implemented. Network data processing system 100 contains network 102, which is the medium used to provide communications links between various devices and computers connected together within network data processing system 100. Network 102 may include connections, such as wire, wireless communication links, or fiber optic cables.

In the depicted example, server 104 is connected to network 102 along with storage unit 106. In addition, clients 108, 110, and 112 are connected to network 102. These clients 108, 110, and 112 may be, for example, personal computers or network computers. In the depicted example, server 104 provides data, such as boot files, operating system images, and applications to clients 108-112. Clients 108, 110, and 112 are clients to server 104. Network data processing system 100 may include additional servers, clients, and other devices not shown. In the depicted example, network data processing system 100 is the Internet with network 102 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, government, educational, and other computer systems that route data and messages. Of course, network data processing system 100 also may be implemented as a number of different types of networks such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN). FIG. 1 is intended as an example, and not as an architectural limitation for the present invention.

Referring to FIG. 2, a block diagram of a data processing system that may be implemented as a server, such as server 104 in FIG. 1, is depicted in accordance with a preferred embodiment of the present invention. Data processing system 200 may be a symmetric multiprocessor (SMP) system including a plurality of processors 202 and 204 connected to system bus 206. Alternatively, a single processor system may be employed. Also connected to system bus 206 is memory controller/cache 208, which provides an interface to local memory 209. I/O bus bridge 210 is connected to system bus 206 and provides an interface to I/O bus 212. Memory controller/cache 208 and I/O bus bridge 210 may be integrated as depicted.

Peripheral component interconnect (PCI) bus bridge 214 connected to I/O bus 212 provides an interface to PCI local bus 216. A number of modems may be connected to PCI local bus 216. Typical PCI bus implementations will support four PCI expansion slots or add-in connectors. Communications links to clients 108-112 in FIG. 1 may be provided through modem 218 and network adapter 220 connected to PCI local bus 216 through add-in boards.

Additional PCI bus bridges 222 and 224 provide interfaces for additional PCI local buses 226 and 228, from which additional modems or network adapters may be supported. In this manner, data processing system 200 allows connections to multiple network computers. A memory-mapped graphics adapter 230 and hard disk 232 may also be connected to I/O bus 212 as depicted, either directly or indirectly.

Those of ordinary skill in the art will appreciate that the hardware depicted in FIG. 2 may vary. For example, other peripheral devices, such as optical disk drives and the like, also may be used in addition to or in place of the hardware depicted. The depicted example is not meant to imply architectural limitations with respect to the present invention.

The data processing system depicted in FIG. 2 may be, for example, an IBM eServer pSeries system, a product of International Business Machines Corporation in Armonk, N.Y., running the Advanced Interactive Executive (AIX) operating system or LINUX operating system.

With reference now to FIG. 3, a block diagram illustrating a data processing system is depicted in which the present invention may be implemented. Data processing system 300 is an example of a client computer. Data processing system 300 employs a peripheral component interconnect (PCI) local bus architecture. Although the depicted example employs a PCI bus, other bus architectures such as Accelerated Graphics Port (AGP) and Industry Standard Architecture (ISA) may be used. Processor 302 and main memory 304 are connected to PCI local bus 306 through PCI bridge 308. PCI bridge 308 also may include an integrated memory controller and cache memory for processor 302. Additional connections to PCI local bus 306 may be made through direct component interconnection or through add-in boards. In the depicted example, local area network (LAN) adapter 310, SCSI host bus adapter 312, and expansion bus interface 314 are connected to PCI local bus 306 by direct component connection. In contrast, audio adapter 316, graphics adapter 318, and audio/video adapter 319 are connected to PCI local bus 306 by add-in boards inserted into expansion slots. Expansion bus interface 314 provides a connection for a keyboard and mouse adapter 320, modem 322, and additional memory 324. Small computer system interface (SCSI) host bus adapter 312 provides a connection for hard disk drive 326, tape drive 328, and CD-ROM drive 330. Typical PCI local bus implementations will support three or four PCI expansion slots or add-in connectors.

An operating system runs on processor 302 and is used to coordinate and provide control of various components within data processing system 300 in FIG. 3. The operating system may be a commercially available operating system, such as Windows XP, which is available from Microsoft Corporation. An object oriented programming system such as Java may run in conjunction with the operating system and provide calls to the operating system from Java programs or applications executing on data processing system 300. “Java” is a trademark of Sun Microsystems, Inc. Instructions for the operating system, the object-oriented programming system, and applications or programs are located on storage devices, such as hard disk drive 326, and may be loaded into main memory 304 for execution by processor 302.

Those of ordinary skill in the art will appreciate that the hardware in FIG. 3 may vary depending on the implementation. Other internal hardware or peripheral devices, such as flash read-only memory (ROM), equivalent nonvolatile memory, or optical disk drives and the like, may be used in addition to or in place of the hardware depicted in FIG. 3. Also, the processes of the present invention may be applied to a multiprocessor data processing system.

The depicted example in FIG. 3 and above-described examples are not meant to imply architectural limitations. For example, data processing system 300 also may be a notebook computer or hand held computer in addition to taking the form of a PDA. Data processing system 300 also may be a kiosk or a Web appliance.

The present invention provides an improved method, apparatus, and computer instructions for providing autonomic solutions in a network data processing system. The mechanism of the present invention stores solutions generated by users, such as engineers and administrators, in a repository that may be accessed to solve similar problems in various data processing systems in the network data processing system. The mechanism of the present invention provides for the use of a software process that records steps in diagnosing or identifying a software problem as well as a solution. These steps may be recorded in different ways, such as using a script.

Further, with respect to identifying or diagnosing a problem, the user may enter or indicate that the problem has been identified as well as indicate that a solution has been completed successfully. These steps are returned to a server process for addition to a knowledge base. In this manner, the steps may be played back or executed on another data processing system with a similar problem. Also, the mechanism of the present invention may analyze the steps recorded with respect to a current solution for the same problem. This analysis may determine whether steps to the current solution have changed. If the solution is changed, the current solution stored on the knowledge base may be updated with changes found in the new solution. This updating may take place automatically if a change is detected or on some statistical basis with respect to identifying solutions on different data processing systems for the same software problem with respect to the current solution. In this manner, steps in a current solution that may have become invalid may be removed from the knowledge base. This knowledge base is a dynamic and changing database that reflects the current solutions for different problems. In this manner, rules, or steps formed in previous operations for a solution may be modified based on more recent solutions or findings. The application of these rules may be determined by a policy, which is determined and set by the user or the user's information technology (IT) organization.

Turning now to FIG. 4, a diagram illustrating components used in a distributed autonomic solutions repository is depicted in accordance with a preferred embodiment of the present invention. In this illustrative example, client 400 includes software program 402, which has a problem or has caused an error. Client 400 may be, for example, data processing system 300 in FIG. 3. Agent 404 is initiated when a user, such as an administrator or service engineer, analyzes client 400 to identify the problem. The particular problem identified may be associated with some unique identifier assigned for this particular problem. The steps used in diagnosing the problem, as well as the identification of the problem itself, may be stored in script 406 by agent 404. The particular steps are automatically recorded in script 406 without requiring the user to take any active steps beyond initiating agent 404. After the problem is identified, the user may indicate to agent 404 that the problem has been successfully diagnosed. At this point, the user may then take steps to generate a solution to the problem with program 402. These steps also are recorded by agent 404 in script 406. In another implementation of the present invention, agent 404 is started when client 400 is started, and thus continually monitors the system. In this case, the user is not specifically required to initiate the agent as described previously.

In this example, the problem may be a printing problem involving printing of a document or file to a color printer. The user may determine that a particular patch for program 402 is an incorrect patch, or that the printer driver software is configured incorrectly, or the printer driver software is an obsolete or incompatible version. The different steps used in making this diagnosis may include, for example, testing the program with the patch and without the patch with respect to the errors that are generated by program 402, or by updating or replacing the printer driver software or color table. If the user determines that the patch is a bad patch, then the particular errors caused by program 402 and the steps used to diagnose and repair the problem may be stored in script 406. Thereafter, the user initiates a solution or steps to repair program 402. In this example, program 402 may require a different patch or a different sequence of patches. The steps in repairing program 402 are also recorded in script 406.

When the repair is completed, the user may indicate that the repair was successful. In response to a successful result, agent 404 automatically sends script 406 to server process 408 in server 410. Server process 408 in server 410 receives script 406 and stores the script in rules database 412. In this illustrative embodiment, server 410 may be implemented using data processing system 200 in FIG. 2. This server also includes software database 414, which, in these examples, includes the various components needed for solutions. For example, software database 414 may contain patches, replacement dynamic link libraries, replacement executable modules, and configuration parameters. A determination is made as to whether the problem identified for program 402 already has a solution within rules database 412. If a similar solution is present, a comparison is made between the new solution received from agent 404 and the current solution stored in rules database 412. If the solution is different, the current solution may be updated with the new solution. This update may be made after a administrator is notified of the change in steps used to reach the solution for the problem. If the administrator approves of the update, the new solution is used to update the current solution in rules database 412. Additionally, a statistical analysis may be made to determine whether the new solution received from agent 404 is statistically significant to warrant a change in the current solution. This analysis may be made by tracking the problems encountered and solutions received from different clients within the network data processing system to identify how often particular steps have changed with respect to the current solution stored in rules database 412. If the change is identified as one that is significant enough to warrant an update, then the update is made in rules database 412. In this manner, steps that become obsolete or fail to solve the problem may be removed while additional steps needed to solve the particular problem may be added to the solution in rules database 412 for this particular problem.

For example, if the solution to a printing problem such as the problem described above requires the installation of a new printer driver, the new printer driver is installed. If the server begins to receive a large number of previously unreported problems from client systems subsequent to the installation of the new printer driver, the rules engine may determine that the problem is likely caused by the new printer driver. In this case, the server will send to agent 404 the instructions to roll back the printer driver to the previous version. The server will then continue to monitor client 400 to determine if the new error reports diminish or disappear. If so, the server determines that the new printer driver is the reason for the problems and removes the new printer driver as a solution script until a determination can be made as to how to fix the original problem. As soon as the proper determination is made, the solution script is updated to reflect the new solution.

Alternatively, agent 404 may monitor system changes and record those changes rather than recording particular steps taken by a user in fixing the problem. Once the problem has been identified and a solution for the problem has been implemented, the user may indicate to agent 404 that the solution is complete. Agent 404 then identifies all changes made within client 400. These changes may include patches that have been added to program 402, changes in configuration parameters, removal of patches, and other changes to program 402, or to other components within client 400. At that time, agent 404 may send this solution to server process 408 for processing and updating the repository contained within server 410.

Turning now to FIG. 5, a diagram illustrating an illustrative example of a solution is depicted in accordance with a preferred embodiment of the present invention. Solution 500 is an example of a solution recorded by client 400 in FIG. 4. This solution may take the form of scripts, such as script 406 in FIG. 4. In this example, solution 500 contains identifier 502, diagnosis 504, and solution 506. Identifier 502 is a unique identifier used to identify the problem that is being diagnosed and solved. This identifier is used to determine whether a solution is already present in a knowledge base for the particular problem. Solution 500 also includes diagnosis 504 and solution 506. In these examples, diagnosis 504 and solution 506 may take the form of steps recorded while a user is diagnosing and repairing a problem for a client.

Additionally, solution 506 also may take the form or state information identifying changes made in the client to solve the problem. These changes may include, for example, the addition of a patch, or change in configuration parameters in the program or operating system. Additionally, solution 506 may also include the prerequisite or subsequent execution of another solution or solutions, identified by their ID. These solutions may also refer to the prerequisite or subsequent execution of another solution or solutions, thus establishing a relationship and dependency between the solutions.

Turning now to FIG. 6, a diagram illustrating a distribution of a solution from an autonomic knowledge base is depicted in accordance with a preferred embodiment of the present invention. Client 600 contains agent 602 and program 604, and local rules database 606. Agent 602 may be used to monitor program 604 to determine where the failure or error occurs. Agent 602 accesses local rules database 606 in the event that an error occurs. This local rules database may be used to identify a particular problem as well as identify solutions for that problem. Local rules database 606 is updated using rules database 608. This update occurs through server process 610 on server 612. In particular, local rules database 606 may take the form of a copy of rules database 608. When a particular solution is identified for a problem in a program, such as program 604, local rules database 606 may identify various components that are needed to solve the problem. These components may be obtained from software database 614. As described above, this database may include components, such as patches, efixes, dynamic link libraries, and executable modules. In these examples, server process 610 may push updates to agent 602 to update local rules database 606. Further, server process 610 may subscribe to other published knowledge bases and incorporated new procedures and fixes from those systems. In this manner, the knowledge base in rules database 608 may be aggregated and updated as necessary.

The different procedures and identification of problems and solutions are stored in rules database 608, while the different components needed to implement a solution may be stored in software database 614. For example, software database 614 may include executable files, dynamic link libraries, and patches. Depending on the particular implementation, the procedures and the components may be located in the same database or further subdivided and placed into other databases.

In this manner, the mechanism of the present invention provides more than merely a recording facility for steps. This mechanism learns from steps taken by a user identifying and solving a problem by comparing the steps in the solution with changes from currently stored steps for a particular problem to update that solution in the knowledge base. In this manner, the mechanism of the present invention adjusts, extends, and/or augments, in a closed-loop fashion, the knowledge base so that the application of the solutions may be applied to other data processing systems when the same or similar problems are encountered.

For example, if a step calls for an installation of a particular version of a dynamic link library and a later step requires the dynamic link library to be upgraded, the steps may be combined into a single step in which the new upgraded dynamic link library is installed early in the process if possible. If this solution causes problems at a later time, appropriate changes may be made such as generating a solution that removes the new dynamic link library and reinstalls the previous version or an older version.

Further, the mechanism of the present invention gathers statistics on selected operations. An operation, such as upgrading a database for a set of files causes problems at a later point and time, that upgrade may be marked as a trouble spot and sent to the system administrator to decide on whether a change to the solution is needed. The results of this decision may be used to upgrade the current knowledge base. As a result, if the findings require removal of a previously installed patch or program, this operation may be pushed to the client from the server and follow up operations performed on the client if necessary by an agent process.

Turning now to FIG. 7, a flowchart of a process for identifying a diagnosis for a problem is depicted in accordance with a preferred embodiment of the present invention. The process illustrated in FIG. 7 may be implemented in an agent, such as agent 404 in FIG. 4.

The process begins by detecting the beginning of a diagnosis of a problem (step 700). This step may be initiated by a user, at the client, entering the user input indicating that the diagnosis procedure is beginning. Next, steps in the diagnosis are recorded (step 702). These steps may include, for example, diagnosis programs executed by the user, parameter or configuration information examined by the user, in other operations or steps performed by the user. Next, a determination is made as to whether the diagnosis is complete (step 704). If the diagnosis is not complete, the process returns to step 702. Otherwise, a determination is made as to whether the problem has been identified by the user (step 706). The user may indicate that the problem has been identified through a selected user input to the agent.

If the problem has been identified, the recorded steps and the problem identification are stored (step 708) with the process terminating thereafter. If the problem has not been successfully identified, the process terminates without storing the recorded information. After this portion of the process is completed, the user then initiates a solution or repair process.

Turning now to FIG. 8, a flowchart of a solution or repair process is depicted in accordance with a preferred embodiment of the present invention. The process illustrated in FIG. 8 may be implemented in an agent, such as agent 404 in FIG. 4.

The process begins by detecting the beginning of the repair (step 800). This step detects a selected user input indicating that steps are now being taken to repair or solve the problem. These steps are recorded (step 802). Thereafter, a determination is made as to whether the repair has been successfully completed (step 804). If the repair has not been completed, the process returns to step 802. Otherwise, a determination is made as to whether the repair has been successful (step 806). The user provides an input to indicate whether the repair is successful in this particular case in response to a prompt from the agent process. If the repair is successful, these steps are stored with the recorded steps and the problem identification to form a solution (step 808). Thereafter, the solution is sent to the server (step 810) with the process terminating thereafter.

With reference again to step 806, if the repair is not successful, the recorded steps for the diagnosis and solution are discarded (step 812) with the process terminating thereafter.

Turning now to FIG. 9, a flowchart of a process for handling a solution received from an agent is depicted in accordance with a preferred embodiment of the present invention. The process illustrated in FIG. 9 may be implemented in a process, such as server process 408 in FIG. 4.

The process begins by receiving a solution from an agent (step 900). A determination is made as to whether the recorded steps in the solution are present in the rules database for the diagnosed problem (step 902). This determination is made by searching for the problem identification in the rules database. In these examples, the problem identification is a unique identifier for a particular problem. If the recorded steps are found in the rules database, a determination is made as to whether the steps taken to solve the problem in the received solution matched those in the rules database (step 904).

If a match does not occur, differences in the steps are identified (step 906). A notification is then sent to the administrator (step 908). This particular example allows the administrator to determine whether an update should occur. A determination is made as to whether to update the current steps (step 910). If an update is to occur, the steps in the rules database are updated with the new steps in the received solution (step 912) with the process terminating thereafter. This update may include eliminating steps from the current solution as well as adding new steps.

With reference again to step 910, if the current steps are not to be updated, the process terminates without making changes to the rules database. Turning back to step 904, if a match does occur, then the steps in the solution are identical to those in the rules database and no updates are made. In this case, the process terminates. With reference back to step 902, if the solution is not present in the rules database for the diagnosed problem, the steps in the solution are stored in the rules database for this particular problem (step 914) with the process terminating thereafter.

With reference now to FIG. 10, a flowchart of a process for updating a local rules database is depicted in accordance with a preferred embodiment of the present invention. The process illustrated in FIG. 10 may be implemented in an agent, such as agent 404 in FIG. 4. The process begins by connecting to the server (step 1000). Next, updates to the rules database are obtained (step 1002). These updates are then used to update a local rules database (step 1004) with the process terminating thereafter.

Turning to FIG. 11, a flowchart of a process for sending updates in a knowledge base to an agent is depicted in accordance with a preferred embodiment of the present invention. The process illustrated in FIG. 11 may be implemented in a server process, such as server process 610 in FIG. 6. The process begins by checking a schedule (step 1100). The schedule identifies when updates to the knowledge should be sent to clients. A determination is made as to whether an update operation is required (step 1102). If an update operation is required, the update is then pushed or sent to clients of the server process (step 1104) with the process terminating thereafter. If an update is not required, the process terminates without taking any action.

Thus, the present invention provides an improved method, apparatus, and computer instructions for a distributed autonomic solutions repository. In these examples, rules database 412 in FIG. 4 and rules database 608 in FIG. 6 are knowledge bases of solutions to problems that may be encountered by clients. The mechanism of the present invention builds and updates this knowledge base through solutions received from users performing repairs or maintenance procedures on clients. The steps performed by these users are recorded and returned to the knowledge database. New solutions to problems not present in this knowledge database are added to the database. Additionally, if new solutions are received for problems currently having solutions in the knowledge base, a determination is made as to whether an update to the current solution is to be made. This decision with respect to the update may be made by an administrator or other user. Alternatively, updates may be automatically made based on a statistical analysis of the solutions received from agents with respect to current solutions.

Variations described for the present invention can be realized in any combination desirable for each particular application. Thus particular limitations, and/or embodiment enhancements described herein, which may have particular advantages to a particular application need not be used for all applications. Also, not all limitations need be implemented in methods, systems and/or apparatus including one or more concepts of the present invention.

The present invention can be realized in hardware, software, or a combination of hardware and software. A visualization tool according to the present invention can be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system—or other apparatus adapted for carrying out the methods and/or functions described herein—is suitable. A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein. The present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which—when loaded in a computer system—is able to carry out these methods.

Computer program means or computer programs in the present context include any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after conversion to another language, code or notation, and/or reproduction in a different material form.

Thus, the invention includes an article of manufacture which comprises a computer usable medium having computer readable program code means embodied therein for causing a function described above. The computer readable program code means in the article of manufacture comprises computer readable program code means for causing a computer to effect the steps of a method of this invention. Similarly, the present invention may be implemented as a computer program product comprising a computer usable medium having computer readable program code means embodied therein for causing a function described above. The computer readable program code means in the computer program product comprising computer readable program code means for causing a computer to effect one or more functions of this invention. Furthermore, the present invention may be implemented as a program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for causing one or more functions of this invention.

It is noted that the foregoing has outlined some of the more pertinent objects and embodiments of the present invention. This invention may be used for many applications. Thus, although the description is made for particular arrangements and methods, the intent and concept of the invention is suitable and applicable to other arrangements and applications. It will be clear to those skilled in the art that modifications to the disclosed embodiments can be effected without departing from the spirit and scope of the invention. The described embodiments ought to be construed to be merely illustrative of some of the more prominent features and applications of the invention. Other beneficial results can be realized by applying the disclosed invention in a different manner or modifying the invention in ways known to those familiar with the art. 

1. A method for managing software, the method comprising the steps of: identifying, by a client computer, a problem in a program within the client computer using a software agent located within the client computer; recording, by the client computer-using the software agent located within the client computer, diagnostic steps into a script as the diagnostic steps are taken by a user to diagnose the problem within the client computer, wherein the user does not take any action to have the diagnostic steps recorded; recording, by the client computer using the software agent located within the client computer, correction steps into the script as the correction steps are taken by the user to correct the problem within the client computer, wherein the user does not take any action to have the correction steps recorded; responsive to the correction steps correcting the problem within the client computer, sending, by the client computer, a solution that includes the correction steps and a problem identifier associated with the problem automatically to a server computer via a network; responsive to the server computer receiving the solution that includes the correction steps and the problem identifier associated with the problem from the client computer via the network, searching, by the server computer, a rules database in the server computer for a stored solution that includes the problem identifier associated with the problem; responsive to locating the stored solution that includes the problem identifier associated with the problem in the rules database in the server computer, determining, by the server computer, whether the stored solution includes stored correction steps that are the same as the correction steps that corrected the problem within the client computer; responsive to determining that the stored correction steps associated with the stored solution that includes the problem identifier associated with the problem are not the same as the correction steps that corrected the problem within the client computer, identifying, by the server computer, differences between the stored correction steps associated with the stored solution that includes the problem identifier associated with the problem and the correction steps that corrected the problem within the client computer; and updating, by the server computer, the stored solution to include the identified differences between the stored correction steps associated with the stored solution and the correction steps that corrected the problem within the client computer to form a second stored solution.
 2. The method of claim 1, further comprising: responsive to connecting to the server computer by a second client computer, obtaining, by the second client computer, updates to the rules database, wherein the updates include the second stored solution; responsive to the second client computer obtaining the updates, updating, by the second client computer, a local rules database in the second client computer to include the updates; and responsive to an occurrence of the problem in the second client computer, using, by the second client computer, the second stored solution in the local rules database to correct the problem in the second client computer.
 3. The method of claim 1, further comprising: updating, by the server computer, the stored solution to form the second stored solution by eliminating correction steps from the stored correction steps and adding new correction steps to the stored solution with the identified differences.
 4. The method of claim 1, further comprising: receiving, by the server computer, a number of reported problems from client computers subsequent to installation of a new software solution on the client computers; responsive to determining that the installation of the new software solution is causing the number of reported problems from the client computers, sending, by the server computer, instructions to the client computers rolling back the installation of the new software solution to a previous version of the program; determining, by the server computer, whether the number of reported problems from the client computers decreases after rolling back the installation of the new software solution to the previous version of the program on the client computers based on monitoring the client computes; and responsive to determining that the number of reported problems from the client computers decreases after the rolling back of the installation of the new software solution to the previous version of the program on the client computers, removing, by the server computer, the new software solution as a fix for the problem from the rules database.
 5. The method of claim 4, wherein the problem is a printing problem, and wherein the new software solution is a new printer driver software version.
 6. A computer program product stored in a computer readable storage device having computer usable program code embodied therein that is executable by a computer for managing software, the computer program product comprising: computer usable program code for identifying, by a client computer, a problem in a program within the client computer using a software agent located within the client computer; computer usable program code for recording, by the client computer using the software agent located within the client computer, diagnostic steps into a script as the diagnostic steps are taken by a user to diagnose the problem within the client computer, wherein the user does not take any action to have the diagnostic steps recorded; computer usable program code for recording, by the client computer using the software agent located within the client computer, correction steps into the script as the correction steps are taken by the user to correct the problem within the client computer, wherein the user does not take any action to have the correction steps recorded; computer usable program code sending, by the client computer, a solution that includes the correction steps and a problem identifier associated with the problem automatically to a server computer via a network in response to the correction steps correcting the problem within the client computer; computer usable program code searching, by the server computer, a rules database in the server computer for a stored solution that includes the problem identifier associated with the problem in response to the server computer receiving the solution that includes the correction steps and the problem identifier associated with the problem from the client computer via the network; computer usable program code for determining, by the server computer, whether the stored solution includes stored correction steps that are the same as the correction steps that corrected the problem within the client computer in response to locating the stored solution that includes the problem identifier associated with the problem in the rules database in the server computer; computer usable program code for identifying, by the server computer, differences between the stored correction steps associated with the stored solution that includes the problem identifier associated with the problem and the correction steps that corrected the problem within the client computer to form identified differences in response to determining that the stored correction steps associated with the stored solution that includes the problem identifier associated with the problem are not the same as the correction steps that corrected the problem within the client computer; and computer usable program code for updating, by the server computer, the stored solution to include the identified differences between the stored correction steps associated with the stored solution and the correction steps that corrected the problem within the client computer to form a second stored solution.
 7. The computer program product of claim 6, further comprising: computer usable program code for obtaining, by a second client computer, updates to the rules database in responsive to connecting to the server computer by the second client computer, wherein the updates include the second stored solution; computer usable program code for updating, by the second client computer, a local rules database in the second client computer to include the updates in response to the second client computer obtaining the updates; and computer usable program code for using, by the second client computer, the second stored solution in the local rules database to correct the problem in the second client computer in response to an occurrence of the problem in the second client computer.
 8. The computer program product of claim 6, further comprising: computer usable program code for updating, by the server computer, the stored solution to form the second stored solution by eliminating correction steps from the stored correction steps and adding new correction steps to the stored solution with the identified differences.
 9. The computer program product of claim 6, further comprising: computer usable program code for receiving, by the server computer, a number of reported problems from client computers subsequent to installation of a new software solution on the client computers; computer usable program code for sending, by the server computer, instructions to the client computers rolling back the installation of the new software solution to a previous version of the program in response to determining that the installation of the new software solution is causing the number of reported problems from the client computers; computer usable program code for determining, by the server computer, whether the number of reported problems from the client computers decreases after rolling back the installation of the new software solution to the previous version of the program on the client computers based on monitoring the client computes; and computer usable program code for removing, by the server computer, the new software solution as a fix for the problem from the rules database in response to determining that the number of reported problems from the client computers decreases after the rolling back of the installation of the new software solution to the previous version of the program on the client computers.
 10. The computer program product of claim 9, wherein the problem is a printing problem, and wherein the new software solution is a new printer driver software version. 